Skip to main content

This is a new service – your feedback will help us to improve it.

Brighton and Hove City Council

Brownfield land

There is a problem

  • 210 entries must have valid coordinates

SHLAA6009

OrganisationURI
SiteReference
SHLAA6009
SiteNameAddress
Blocks E & F Kingsmere London Road
GeoX
POINT(-0.151263 50.846981)
GeoY
POINT(-0.151263 50.846981)
SiteplanURL
https://new.brighton-hove.gov.uk/sites/default/files/planning_bc_regen/policy/brownfield-sites/shlaa6009-blocks-e-f-kingsmere-london-road.pdf
Hectares
0.09
OwnershipStatus
not-owned-by-a-public-authority
PlanningStatus
permissioned
PermissionType
other
PermissionDate
2020-09-30
PlanningHistory
https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=QEOUREDM0P900|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR61DMXE491|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR62DMXE324|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR63DMXE573|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR6IDMXE893|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR6ODMXE115|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR6YDMXE545|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR70DMXE321
Deliverable
yes
NetDwellingsRangeFrom
18
NetDwellingsRangeTo
18
HazardousSubstances
Notes
BH2021/02263 Prior Approval for 18 units Not Started 21/22
FirstAddedDate
2017-09-19
LastUpdatedDate
2022-12-05
EndDate
GeoX,GeoY

Geometry must use WGS84, OSGB or Mercator coordinates

How to improve Brighton and Hove City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL